Summary

Made quite a few edits:

• removed deprecated TellorX mock solidtity contracts and SampleXReporter
• Edited the SampleFlexReporter solidity contract to work and fixed test, this wasn't working before
• Added base_fee flag to allow user to input that in the cli if they wish (its another way to estimate the max fee)
• Added a request-withdraw and a stake command to be able to call the respective methods in the oracle contract separate from the reporter command.
• Separate common command options into two See here
• Decreased the max priority fee (aka tip) default range to 3 gwei since 80 is too high.
• Adjust Diva reporter to use GasFees object to generate gas fields when reporting and also consolidate the code to only adapt the method it needs instead of overwriting the report_once and report methods.
• Add stake command
• Same as diva with Flashbots reporter
• Remove redundant code in RNG reporter.
• Added GasFees class that would be inherited and used to generated gas params for the reporter.
• Add StakeInfo class to be used in the reporter to monitor when stake amount is changed or reporter is slashed currently the reporter will auto stake if any of these events happen.
• Broke up some of the code in the reporter for easier readability and usage

Steps Taken to QA Changes

• Added new tests for the new classes plus another reporter test to check the changes
• Consolidated the previous reporter tests into one
• Fixed tests that were broken due to the changes

Example transactions using cli:

• withdraw txn
• stake txn
• request withdraw
• report

Checklist

This pull request is:

• A documentation error, docs update, or typographical error fix
  • No tests or issue needed
• A code fix
  • Please reference the related issue by including "Closes <link to issue>" in this Pull Request's summary section.
    • If no issue exists, please create a bug report issue
  • Please include tests. Fixes without tests will not be accepted unless it's related to the documentation only.
  • Please make sure docs are updated if need be
• A feature implementation
  • Please reference the related issue by including "Closes <link to issue>" in this Pull Request's summary section.
    • If no issue exists, please create a feature enhancement issue
  • Please include tests
  • Please make sure docs updates are both thorough and easy to reproduce by somebody with limited knowledge of the feature that you are submitting

Happy engineering!